Skip to content

fix(repo): stop scraping a retired domain, restore the files it corrupted - #12

Merged
jiashuoz merged 1 commit into
mainfrom
fix/sdk-repo-hygiene
Sep 4, 2026
Merged

fix(repo): stop scraping a retired domain, restore the files it corrupted#12
jiashuoz merged 1 commit into
mainfrom
fix/sdk-repo-hygiene

Conversation

@jiashuoz

@jiashuoz jiashuoz commented Sep 4, 2026

Copy link
Copy Markdown
Member

What

.github/workflows/sync-content.yml generated repo content by fetching docs from agentdrive.run with curl -sSf. That domain was retired and now answers 301. curl -sSf neither follows a redirect nor treats one as an error, so the job wrote the Cloudflare redirect page into five files and committed them to this public repo:

skills/agentdrive/SKILL.md
docs/setup.md
docs/auth.md
docs/api.md
connector/llms.txt

Each of those files currently contains nothing but a 301 HTML page on main.

Changes

  • Delete sync-content.yml. Scraping a production website to generate repo content is the defect, not the redirect. Content is authored in-repo from now on.
  • Delete the top-level skills/ directory. It duplicated the authored skill at plugin/skills/agentdrive/SKILL.md, and this copy was the corrupted one. The authored copy is untouched by this PR.
  • Rewrite the four remaining files as authored Markdown.
  • Repoint dead hosts in README.md and AGENTS.md.
  • publish.yml: the Go module tagger was committing as support@agentdrive.run, a dead address.
was now
api.agentdrive.run/mcp drive.mcp.tokencanopy.com/mcp
agentdrive.run tokencanopy.com
support@agentdrive.run hello@mnexa.ai

Verification

  • docs/api.md enumerates operations read from sdk/openapi.json rather than restating a contract from memory. All 63 operations match the committed spec exactly; none invented:
    real ops in openapi.json: 63   claimed in api.md: 63   claimed but not in contract: 0
    
  • Dead-host sweep across the whole repo after merging with #(plugin PR): the only remaining agentdrive.run mention is one prose sentence describing the registry problem. Zero in sdk/.
  • Sign-in URL and DCR endpoint used in docs/auth.md verified live (app.tokencanopy.com → 200; auth.tokencanopy.com/oidc/reg from the published AS metadata).

Notes

Independent of the companion plugin PR — the two touch disjoint files and were test-merged cleanly before either was pushed.

Nothing here republishes the MCP Registry entry, which still advertises the dead endpoint. That needs a DNS-verified republish and is a separate decision.

🤖 Generated with Claude Code

https://claude.ai/code/session_01W1nxC2LaqTPrix7CL4Ehuv

…pted

`.github/workflows/sync-content.yml` fetched documentation from
`agentdrive.run` with `curl -sSf`. That domain was retired and now answers
301. `curl -sSf` neither follows a redirect nor treats one as an error, so
the job wrote the Cloudflare redirect page into five files and committed
them to this public repo:

  skills/agentdrive/SKILL.md
  docs/setup.md
  docs/auth.md
  docs/api.md
  connector/llms.txt

Delete the workflow — generating repo content by scraping a production
website is the defect, not the redirect. The content is authored in-repo
from now on.

Delete the top-level `skills/` directory outright: it was a duplicate of the
authored skill at `plugin/skills/agentdrive/SKILL.md`, and this copy is the
corrupted one.

Rewrite the remaining four files as authored Markdown. `docs/api.md`
enumerates operations read from `sdk/openapi.json` rather than restating a
contract from memory; all 63 match the committed spec.

Repoint every dead host and address:

  api.agentdrive.run/mcp  ->  drive.mcp.tokencanopy.com/mcp
  agentdrive.run          ->  tokencanopy.com
  support@agentdrive.run  ->  hello@mnexa.ai

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01W1nxC2LaqTPrix7CL4Ehuv
@jiashuoz
jiashuoz merged commit 6bf734f into main Sep 4, 2026
4 checks passed
@jiashuoz
jiashuoz deleted the fix/sdk-repo-hygiene branch September 4, 2026 03:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant